Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f85a60412619b260a354cfc0cdfaaa0b74f0767e05cb990627455f98fe4b4b6

Tx prefix hash: d5f6db80d744d0fe33a82835343cf509215a0c3bf566fbf3ffa53ff1cdeaa6d6
Tx public key: a028f1a4ae91af6e6532de33dc68f417aa124deca25c3ddab730609643fa0e6b
Timestamp: 1713051531 Timestamp [UCT]: 2024-04-13 23:38:51 Age [y:d:h:m:s]: 01:018:09:34:53
Block: 999924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274135 RingCT/type: yes/0
Extra: 01a028f1a4ae91af6e6532de33dc68f417aa124deca25c3ddab730609643fa0e6b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d1da6a5869e3aef7ec5b72cc351d89045e8f68b926e968b633fe82eedc91e9f 0.600000000000 1460412 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": 999934, "vin": [ { "gen": { "height": 999924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d1da6a5869e3aef7ec5b72cc351d89045e8f68b926e968b633fe82eedc91e9f" } } ], "extra": [ 1, 160, 40, 241, 164, 174, 145, 175, 110, 101, 50, 222, 51, 220, 104, 244, 23, 170, 18, 77, 236, 162, 92, 61, 218, 183, 48, 96, 150, 67, 250, 14, 107, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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