Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78992cffdc62f4af6971cbc2517c9ea0548d9393583d88c35230a623542fa077

Tx prefix hash: 2bb3c8b2ce415f8f04081032c99d1d63a8afe971d1370f4c5be3850b0f0e6c18
Tx public key: bb6e8d919da203329cf1e2e4f9ab5b457a3c175269fca87888bb8881c0ef7d6d
Timestamp: 1721803119 Timestamp [UCT]: 2024-07-24 06:38:39 Age [y:d:h:m:s]: 01:118:08:01:50
Block: 1072498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343087 RingCT/type: yes/0
Extra: 01bb6e8d919da203329cf1e2e4f9ab5b457a3c175269fca87888bb8881c0ef7d6d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86ea056ef6cd07c2f4f6d0c43e9d2633d6fb81b1da01a060eb44b4093728e791 0.600000000000 1544971 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": 1072508, "vin": [ { "gen": { "height": 1072498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86ea056ef6cd07c2f4f6d0c43e9d2633d6fb81b1da01a060eb44b4093728e791" } } ], "extra": [ 1, 187, 110, 141, 145, 157, 162, 3, 50, 156, 241, 226, 228, 249, 171, 91, 69, 122, 60, 23, 82, 105, 252, 168, 120, 136, 187, 136, 129, 192, 239, 125, 109, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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