Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba8b1ebd5f639c8d4f349215fe1f80e7f45d5a14c11b6c7e3def3c83a8d3e648

Tx prefix hash: bcb741086ca233344b5ed73108c6ea5a407fe8a94a635fae29f6d672e12d1265
Tx public key: b253e0c7e8343275143963c8a562834ac29fe35ff870ed907f371434b89f94bc
Timestamp: 1728682660 Timestamp [UCT]: 2024-10-11 21:37:40 Age [y:d:h:m:s]: 00:182:09:59:30
Block: 1129539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130166 RingCT/type: yes/0
Extra: 01b253e0c7e8343275143963c8a562834ac29fe35ff870ed907f371434b89f94bc02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a21689ac21fe8bcfe93a7df72a20a6f0f1d5ad26759a4be93fa4d4c889ca05 0.600000000000 1612366 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": 1129549, "vin": [ { "gen": { "height": 1129539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a21689ac21fe8bcfe93a7df72a20a6f0f1d5ad26759a4be93fa4d4c889ca05" } } ], "extra": [ 1, 178, 83, 224, 199, 232, 52, 50, 117, 20, 57, 99, 200, 165, 98, 131, 74, 194, 159, 227, 95, 248, 112, 237, 144, 127, 55, 20, 52, 184, 159, 148, 188, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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