Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6bb186ef1ae3d4aac674f09aec63339a80b436b983b67adba5a54a3af740ee

Tx prefix hash: 9b0cfd597e52a9fae6832d248ae0f631e66fae88bb4c826c436e104df542ebe6
Tx public key: 24c4f99840d2b849489c89b777d49f444e85c107c4f56b43c174337b430bc60e
Timestamp: 1693070124 Timestamp [UCT]: 2023-08-26 17:15:24 Age [y:d:h:m:s]: 01:247:12:05:45
Block: 834466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438046 RingCT/type: yes/0
Extra: 0124c4f99840d2b849489c89b777d49f444e85c107c4f56b43c174337b430bc60e02110000000f75e3f0e9000000000000000000

1 output(s) for total of 1.054551559000 dcy

stealth address amount amount idx
00: bca58c9363ff7a58b4b844c50a30eba710f128ff8d760c122544fb68d9d7df7b 1.054551559000 1286960 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": 834476, "vin": [ { "gen": { "height": 834466 } } ], "vout": [ { "amount": 1054551559, "target": { "key": "bca58c9363ff7a58b4b844c50a30eba710f128ff8d760c122544fb68d9d7df7b" } } ], "extra": [ 1, 36, 196, 249, 152, 64, 210, 184, 73, 72, 156, 137, 183, 119, 212, 159, 68, 78, 133, 193, 7, 196, 245, 107, 67, 193, 116, 51, 123, 67, 11, 198, 14, 2, 17, 0, 0, 0, 15, 117, 227, 240, 233, 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