Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3ca4b5ad4a1db48449cd851b01f95ff9a09371ea9028f5bd3beecafff9a7a27

Tx prefix hash: 96b72a1b68d0e8275360e10546d510225cbe75d55db2b147cf8e16aaf802d04a
Tx public key: a14b9e9af693e17eff4455f9e8abb1d78804ca65e469c044d6c6226a4e065547
Timestamp: 1663453090 Timestamp [UCT]: 2022-09-17 22:18:10 Age [y:d:h:m:s]: 03:048:11:39:34
Block: 590175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 814533 RingCT/type: yes/0
Extra: 01a14b9e9af693e17eff4455f9e8abb1d78804ca65e469c044d6c6226a4e06554702110000000333af99f4000000000000000000

1 output(s) for total of 6.799943526000 dcy

stealth address amount amount idx
00: 841f1dc7cf31f93f7595304e4f56847727a3a1ed4ebafe08805431cd9d2a6ff8 6.799943526000 1024566 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": 590185, "vin": [ { "gen": { "height": 590175 } } ], "vout": [ { "amount": 6799943526, "target": { "key": "841f1dc7cf31f93f7595304e4f56847727a3a1ed4ebafe08805431cd9d2a6ff8" } } ], "extra": [ 1, 161, 75, 158, 154, 246, 147, 225, 126, 255, 68, 85, 249, 232, 171, 177, 215, 136, 4, 202, 101, 228, 105, 192, 68, 214, 198, 34, 106, 78, 6, 85, 71, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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