Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cf6412820c6380d866efbe4a50c1382443b2944d073685c7bfc923085d1c31c

Tx prefix hash: a0017d977d447fe3b73fe8555b75472c2bf011d1524a06d066255a501d2e59d8
Tx public key: 51bffe21b435619ca9a469670c4c7d67c6e2cee9216d7e6ccfde322fb88a74a7
Timestamp: 1734730353 Timestamp [UCT]: 2024-12-20 21:32:33 Age [y:d:h:m:s]: 00:015:08:55:28
Block: 1179586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10980 RingCT/type: yes/0
Extra: 0151bffe21b435619ca9a469670c4c7d67c6e2cee9216d7e6ccfde322fb88a74a70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a17f17ca39541b5309a1c7509df5bf6da4a0458b66a9426752a65ddbe66c5fdc 0.600000000000 1665983 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": 1179596, "vin": [ { "gen": { "height": 1179586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a17f17ca39541b5309a1c7509df5bf6da4a0458b66a9426752a65ddbe66c5fdc" } } ], "extra": [ 1, 81, 191, 254, 33, 180, 53, 97, 156, 169, 164, 105, 103, 12, 76, 125, 103, 198, 226, 206, 233, 33, 109, 126, 108, 207, 222, 50, 47, 184, 138, 116, 167, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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