Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 846f0b12b0cee94763bffeb5b80a2d108c194978e37c8ba41eac7893b33224d9

Tx prefix hash: b21df907ad73e1ed37c3bf535d225511755bac9db84ab31f44168cf0e78b17fa
Tx public key: ce53cae4473e2625e43b39d9e5c3402f49d6555db9802b2ea6b57a818b866d3f
Timestamp: 1711131591 Timestamp [UCT]: 2024-03-22 18:19:51 Age [y:d:h:m:s]: 01:003:03:37:18
Block: 984053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263199 RingCT/type: yes/0
Extra: 01ce53cae4473e2625e43b39d9e5c3402f49d6555db9802b2ea6b57a818b866d3f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f18a2335f3e25570d3636f69bf52160d1c1b892aa89f59565c765315ff562e1 0.600000000000 1444208 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": 984063, "vin": [ { "gen": { "height": 984053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f18a2335f3e25570d3636f69bf52160d1c1b892aa89f59565c765315ff562e1" } } ], "extra": [ 1, 206, 83, 202, 228, 71, 62, 38, 37, 228, 59, 57, 217, 229, 195, 64, 47, 73, 214, 85, 93, 185, 128, 43, 46, 166, 181, 122, 129, 139, 134, 109, 63, 2, 17, 0, 0, 0, 2, 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