Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b70e484486951c2a228325debc921a7deb5361b1523ea4c7ffa7d312e76241d9

Tx prefix hash: 58d31556f4322b0f50b9066fb1dd2e40fd8dca3beb228bc1cb1e40e99e9a1d6b
Tx public key: e77947369e5e3d6871b286fdd1acd1c072548f7e31b291b7d92fc2a8a103e56d
Timestamp: 1706621168 Timestamp [UCT]: 2024-01-30 13:26:08 Age [y:d:h:m:s]: 01:030:07:59:45
Block: 946617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282729 RingCT/type: yes/0
Extra: 01e77947369e5e3d6871b286fdd1acd1c072548f7e31b291b7d92fc2a8a103e56d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b44f376bee5db2d68829d825cd2bfd081f971dda427b39fa9b01de99ceb6ea39 0.600000000000 1404951 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": 946627, "vin": [ { "gen": { "height": 946617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b44f376bee5db2d68829d825cd2bfd081f971dda427b39fa9b01de99ceb6ea39" } } ], "extra": [ 1, 231, 121, 71, 54, 158, 94, 61, 104, 113, 178, 134, 253, 209, 172, 209, 192, 114, 84, 143, 126, 49, 178, 145, 183, 217, 47, 194, 168, 161, 3, 229, 109, 2, 17, 0, 0, 0, 1, 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