Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c03795a84fac66b2c0a6da7dc858e749f3e9d05ca5b456de011962791d3d1bb7

Tx prefix hash: cc046552f4a2a6cc44c1faf42b19e4f7478004bf7c6eb64ff3bdad10a30ca0f0
Tx public key: 9c61fb5d7d9a3d9153106f6ba47f5a7e7428432b2885103f009a39363ccd15db
Timestamp: 1745290165 Timestamp [UCT]: 2025-04-22 02:49:25 Age [y:d:h:m:s]: 00:213:20:10:41
Block: 1266706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150555 RingCT/type: yes/0
Extra: 019c61fb5d7d9a3d9153106f6ba47f5a7e7428432b2885103f009a39363ccd15db0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354eb7167496ef628061eef78fee8bce8e9cce8976db0a300f44e85abbdcad1b 0.600000000000 1753927 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": 1266716, "vin": [ { "gen": { "height": 1266706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354eb7167496ef628061eef78fee8bce8e9cce8976db0a300f44e85abbdcad1b" } } ], "extra": [ 1, 156, 97, 251, 93, 125, 154, 61, 145, 83, 16, 111, 107, 164, 127, 90, 126, 116, 40, 67, 43, 40, 133, 16, 63, 0, 154, 57, 54, 60, 205, 21, 219, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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