Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84af5e6f62a409df8a6e4e8970350bcbdeb9379285737baf7a96cb3b427f39d1

Tx prefix hash: a4b357da27c5f9628d4586afc7bb1ef790cfa3d3b1b7ffaf2f02dacdbf5c0121
Tx public key: a000b06d327a63d8eec16bd06fe5c14eae1747290a6f6229b4ca9aa21cb2508b
Timestamp: 1675041251 Timestamp [UCT]: 2023-01-30 01:14:11 Age [y:d:h:m:s]: 02:113:07:55:36
Block: 685722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 602643 RingCT/type: yes/0
Extra: 01a000b06d327a63d8eec16bd06fe5c14eae1747290a6f6229b4ca9aa21cb2508b02110000000e835e4d22000000000000000000

1 output(s) for total of 3.280335708000 dcy

stealth address amount amount idx
00: bc2b03fe64afeff635126605e316a1fb927addbb89ac7e94e1b32a27ddc0abee 3.280335708000 1128097 of 0

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": 685732, "vin": [ { "gen": { "height": 685722 } } ], "vout": [ { "amount": 3280335708, "target": { "key": "bc2b03fe64afeff635126605e316a1fb927addbb89ac7e94e1b32a27ddc0abee" } } ], "extra": [ 1, 160, 0, 176, 109, 50, 122, 99, 216, 238, 193, 107, 208, 111, 229, 193, 78, 174, 23, 71, 41, 10, 111, 98, 41, 180, 202, 154, 162, 28, 178, 80, 139, 2, 17, 0, 0, 0, 14, 131, 94, 77, 34, 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