Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61e04f28577cb9f6ddcb581325c6e56bbb32ea50957812bf0d53d1000e38169e

Tx prefix hash: 357d8772e77f2146896eaa1510791735a2fe8e7602ad028efd94fce49a97ecd5
Tx public key: 2ba15ae8bf1b1c3f53e9df35cd3ae601ca7113cff78f5510d805fcfcfe7979ed
Timestamp: 1718801774 Timestamp [UCT]: 2024-06-19 12:56:14 Age [y:d:h:m:s]: 00:166:05:36:19
Block: 1047627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118965 RingCT/type: yes/0
Extra: 012ba15ae8bf1b1c3f53e9df35cd3ae601ca7113cff78f5510d805fcfcfe7979ed0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbb0a24a1affc6840827daf3f2ac3c09a0ea8522ff1d0263341df6b17a9a0cd8 0.600000000000 1517498 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": 1047637, "vin": [ { "gen": { "height": 1047627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbb0a24a1affc6840827daf3f2ac3c09a0ea8522ff1d0263341df6b17a9a0cd8" } } ], "extra": [ 1, 43, 161, 90, 232, 191, 27, 28, 63, 83, 233, 223, 53, 205, 58, 230, 1, 202, 113, 19, 207, 247, 143, 85, 16, 216, 5, 252, 252, 254, 121, 121, 237, 2, 17, 0, 0, 0, 3, 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