Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfac68654d7ed685afdd262baf5f31d6ec566d8a07e90ca0c08a8554bd00f0bc

Tx prefix hash: b7a5239a3db5c4df249381921e97528aae1bbba8155b31abcb2de75c030a1a39
Tx public key: cf3f984dbe5318251aa7d9cbf3ae6b55c83ee7f44c029cc10e150428dbd80050
Timestamp: 1577728068 Timestamp [UCT]: 2019-12-30 17:47:48 Age [y:d:h:m:s]: 05:137:01:44:51
Block: 35204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247753 RingCT/type: yes/0
Extra: 01cf3f984dbe5318251aa7d9cbf3ae6b55c83ee7f44c029cc10e150428dbd800500211000000068a2ee0d9000000000000000000

1 output(s) for total of 469.197175202000 dcy

stealth address amount amount idx
00: dc7f856e69c133361a79baeb6da6ee9831d5aa4228688f0f49fb0b9a93b70d2d 469.197175202000 59294 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": 35214, "vin": [ { "gen": { "height": 35204 } } ], "vout": [ { "amount": 469197175202, "target": { "key": "dc7f856e69c133361a79baeb6da6ee9831d5aa4228688f0f49fb0b9a93b70d2d" } } ], "extra": [ 1, 207, 63, 152, 77, 190, 83, 24, 37, 26, 167, 217, 203, 243, 174, 107, 85, 200, 62, 231, 244, 76, 2, 156, 193, 14, 21, 4, 40, 219, 216, 0, 80, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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