Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e2f2cebcc2ff2d86ec27b3f214173f607e94bc1c5632563354e24c32b6dafd3

Tx prefix hash: 2f8a3519c2e89a0e5b5388fd6068f3d22439a4f2d0b74dd99da21a9503d6563a
Tx public key: a05aada8c6f5ff3d4eaf0241fc177a93ce8244091d68c11dc715df875f1f55b9
Timestamp: 1728679668 Timestamp [UCT]: 2024-10-11 20:47:48 Age [y:d:h:m:s]: 00:193:06:44:39
Block: 1129513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137931 RingCT/type: yes/0
Extra: 01a05aada8c6f5ff3d4eaf0241fc177a93ce8244091d68c11dc715df875f1f55b902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddedde1e9b871e5e037d6ac42ef303576120a0d3af44c36f8deed87687b5d70f 0.600000000000 1612340 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": 1129523, "vin": [ { "gen": { "height": 1129513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddedde1e9b871e5e037d6ac42ef303576120a0d3af44c36f8deed87687b5d70f" } } ], "extra": [ 1, 160, 90, 173, 168, 198, 245, 255, 61, 78, 175, 2, 65, 252, 23, 122, 147, 206, 130, 68, 9, 29, 104, 193, 29, 199, 21, 223, 135, 95, 31, 85, 185, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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