Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e243be896f21fbc81911ab6f481796a0ba277e68a4d557a318e72373639395c

Tx prefix hash: beb999f2be5411380a167b6af5d12ddca9cc675dcaddf5e0722380e3ae61f613
Tx public key: 3b3a18a609dfccfa827b7238ad594d7bc1fc83fbe4519f4bec06a4e0cd1842c9
Timestamp: 1719839295 Timestamp [UCT]: 2024-07-01 13:08:15 Age [y:d:h:m:s]: 00:282:05:25:21
Block: 1056223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201654 RingCT/type: yes/0
Extra: 013b3a18a609dfccfa827b7238ad594d7bc1fc83fbe4519f4bec06a4e0cd1842c90211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 696cba7c6d136150b58e9bc2abd6683a819b83a8d2e36b31fffa2e1691e9a66c 0.600000000000 1526636 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": 1056233, "vin": [ { "gen": { "height": 1056223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "696cba7c6d136150b58e9bc2abd6683a819b83a8d2e36b31fffa2e1691e9a66c" } } ], "extra": [ 1, 59, 58, 24, 166, 9, 223, 204, 250, 130, 123, 114, 56, 173, 89, 77, 123, 193, 252, 131, 251, 228, 81, 159, 75, 236, 6, 164, 224, 205, 24, 66, 201, 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