Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afaedfb48cfb32c380aef7d5f8802ad9eb96e08909024a6c06debe9c96225308

Tx prefix hash: 24f3d715dcfff6e3740eb7958475963bf54a009fc7b173126f94de4dfd161466
Tx public key: 6f0d21964ad7a84034d4a48df690ecb02cae1dc4ab95dcd1348ad1b746b2518e
Timestamp: 1720334674 Timestamp [UCT]: 2024-07-07 06:44:34 Age [y:d:h:m:s]: 00:273:16:55:52
Block: 1060328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195543 RingCT/type: yes/0
Extra: 016f0d21964ad7a84034d4a48df690ecb02cae1dc4ab95dcd1348ad1b746b2518e0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4af5a41ab47657e328954dc99213953cbf87d8e782942a45f793dbdbdfd54080 0.600000000000 1530805 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": 1060338, "vin": [ { "gen": { "height": 1060328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4af5a41ab47657e328954dc99213953cbf87d8e782942a45f793dbdbdfd54080" } } ], "extra": [ 1, 111, 13, 33, 150, 74, 215, 168, 64, 52, 212, 164, 141, 246, 144, 236, 176, 44, 174, 29, 196, 171, 149, 220, 209, 52, 138, 209, 183, 70, 178, 81, 142, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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