Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 681b78bcdf32652529bb9e7900ba70bdf7f6dce7f40ce73277c71b886755fb43

Tx prefix hash: 60c08ef685d35888072e9dac28686ab387d1d8d33bc2e8981a453331cf02769a
Tx public key: f72440e54ba32f319c9d1ca32cf8fea1d8742ecf12d9e365e81add5f4587eaa4
Timestamp: 1733431033 Timestamp [UCT]: 2024-12-05 20:37:13 Age [y:d:h:m:s]: 00:142:16:40:41
Block: 1168810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101797 RingCT/type: yes/0
Extra: 01f72440e54ba32f319c9d1ca32cf8fea1d8742ecf12d9e365e81add5f4587eaa40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 229fbe578188b9597fbdde88b57a5a8e8f0bd3ea67973b586e5ab604a477308a 0.600000000000 1654521 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": 1168820, "vin": [ { "gen": { "height": 1168810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "229fbe578188b9597fbdde88b57a5a8e8f0bd3ea67973b586e5ab604a477308a" } } ], "extra": [ 1, 247, 36, 64, 229, 75, 163, 47, 49, 156, 157, 28, 163, 44, 248, 254, 161, 216, 116, 46, 207, 18, 217, 227, 101, 232, 26, 221, 95, 69, 135, 234, 164, 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