Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9400c5e5a9b7c29bf073cf84deffdc7cb9249522de1516cfb63f407f9d2bcc

Tx prefix hash: 3db3511b42fbf18594931cf87442e1a6605a8632f57d9564eb09e4ddb47b6c48
Tx public key: 316bc8d2023a136ce93a5ad12264727e6d61aab1fbedb4bb57a4c4cbc8044e6b
Timestamp: 1719490527 Timestamp [UCT]: 2024-06-27 12:15:27 Age [y:d:h:m:s]: 01:194:19:45:06
Block: 1053327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397869 RingCT/type: yes/0
Extra: 01316bc8d2023a136ce93a5ad12264727e6d61aab1fbedb4bb57a4c4cbc8044e6b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc10ffcc3a15a6100b9f7f2988ba3778c90cfadd76fddec39c8d0ad55a7589b 0.600000000000 1523674 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": 1053337, "vin": [ { "gen": { "height": 1053327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc10ffcc3a15a6100b9f7f2988ba3778c90cfadd76fddec39c8d0ad55a7589b" } } ], "extra": [ 1, 49, 107, 200, 210, 2, 58, 19, 108, 233, 58, 90, 209, 34, 100, 114, 126, 109, 97, 170, 177, 251, 237, 180, 187, 87, 164, 196, 203, 200, 4, 78, 107, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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