Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7f57f48d2bc761fdceab88f00a430aa2f4d5b9e1bf23a3b0c084d844e855578

Tx prefix hash: 94f0cdaaadd3167e03c5d6a0a597a0153626efc40b32492ca0879394523ad9cb
Tx public key: e57509f91abb429d305718a88dbf82b3b586625515a65fc626bc05ef32448c82
Timestamp: 1709502152 Timestamp [UCT]: 2024-03-03 21:42:32 Age [y:d:h:m:s]: 01:049:09:03:09
Block: 970526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296300 RingCT/type: yes/0
Extra: 01e57509f91abb429d305718a88dbf82b3b586625515a65fc626bc05ef32448c820211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b60a6e27dfb3bbb50e966beb4b5619a97ea7b5c8e9991df5999625dddc03b88d 0.600000000000 1430385 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": 970536, "vin": [ { "gen": { "height": 970526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b60a6e27dfb3bbb50e966beb4b5619a97ea7b5c8e9991df5999625dddc03b88d" } } ], "extra": [ 1, 229, 117, 9, 249, 26, 187, 66, 157, 48, 87, 24, 168, 141, 191, 130, 179, 181, 134, 98, 85, 21, 166, 95, 198, 38, 188, 5, 239, 50, 68, 140, 130, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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