Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353e53fbd7798d94e070fcb3fb924fff624279823eb722fd74498379d0c9ce1f

Tx prefix hash: 65ad1e082072a5a7f63f2a7328c81f07a45173d2c69da8a6262d408306691332
Tx public key: a72ed5cc2873433cf6e040bd0ae5df1a472e612fb24861d66e1708791dfc69b0
Timestamp: 1737600329 Timestamp [UCT]: 2025-01-23 02:45:29 Age [y:d:h:m:s]: 00:050:23:17:20
Block: 1203273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36259 RingCT/type: yes/0
Extra: 01a72ed5cc2873433cf6e040bd0ae5df1a472e612fb24861d66e1708791dfc69b0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b0d6c0e856f393ad0be1c23a8785187dc1f5ceb497dde062d0f81941a6ac906 0.600000000000 1689948 of 15

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": 1203283, "vin": [ { "gen": { "height": 1203273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b0d6c0e856f393ad0be1c23a8785187dc1f5ceb497dde062d0f81941a6ac906" } } ], "extra": [ 1, 167, 46, 213, 204, 40, 115, 67, 60, 246, 224, 64, 189, 10, 229, 223, 26, 71, 46, 97, 47, 178, 72, 97, 214, 110, 23, 8, 121, 29, 252, 105, 176, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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