Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b8718f25502055dd63d6a4aad617ddcda012084317046ae58db45f1d2a24fe71

Tx prefix hash: 435b5ca880d094aa98c6049d7cd984559188443a3f8480e8b5471b737d6f2360
Tx public key: f9cf3a9c817457104ce5eb5a1296931efe7d2dd9ace411416c8c556d7d7695ec
Timestamp: 1578239284 Timestamp [UCT]: 2020-01-05 15:48:04 Age [y:d:h:m:s]: 05:035:21:17:45
Block: 39301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175507 RingCT/type: yes/0
Extra: 01f9cf3a9c817457104ce5eb5a1296931efe7d2dd9ace411416c8c556d7d7695ec021100000039391a8d0e000000000000000000

1 output(s) for total of 454.757971962000 dcy

stealth address amount amount idx
00: 32fa72caeec616e2e46e65e7c15ab60d4bc10aa27d732e074d4dee40fdbf74ed 454.757971962000 67664 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 39311, "vin": [ { "gen": { "height": 39301 } } ], "vout": [ { "amount": 454757971962, "target": { "key": "32fa72caeec616e2e46e65e7c15ab60d4bc10aa27d732e074d4dee40fdbf74ed" } } ], "extra": [ 1, 249, 207, 58, 156, 129, 116, 87, 16, 76, 229, 235, 90, 18, 150, 147, 30, 254, 125, 45, 217, 172, 228, 17, 65, 108, 140, 85, 109, 125, 118, 149, 236, 2, 17, 0, 0, 0, 57, 57, 26, 141, 14, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8