Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef125a9dddff341638c8c3584d110e86ab32eb9e12f6c4ed1145132a4844e949

Tx prefix hash: 796db78ca95cd2f4c09c4d2b03793aea4726edd5bea5116bc17d44f069c80248
Tx public key: 724b271bc0882493a292f39aa1223f49b398f86b5ea4a4e423d3bb2c018ad62d
Timestamp: 1722783128 Timestamp [UCT]: 2024-08-04 14:52:08 Age [y:d:h:m:s]: 00:265:07:13:33
Block: 1080624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189527 RingCT/type: yes/0
Extra: 01724b271bc0882493a292f39aa1223f49b398f86b5ea4a4e423d3bb2c018ad62d02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aad6bf30b49df6f016032f668b300dd96fe376415882c4765a546e5f983a1488 0.600000000000 1554059 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": 1080634, "vin": [ { "gen": { "height": 1080624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aad6bf30b49df6f016032f668b300dd96fe376415882c4765a546e5f983a1488" } } ], "extra": [ 1, 114, 75, 39, 27, 192, 136, 36, 147, 162, 146, 243, 154, 161, 34, 63, 73, 179, 152, 248, 107, 94, 164, 164, 228, 35, 211, 187, 44, 1, 138, 214, 45, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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