Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1a40deea1c23c2609d3c6ff6e75e5ecde4103eb5fb753bd7952fe16d9a9d1b

Tx prefix hash: 5bb1a78e010777e9271afa143158a6845b9a8de79e8129b0455b89119119dae6
Tx public key: c64e36cf66b7addd8e6bb34075c23a3b7b0606088314c2a27ca627ef575125cc
Timestamp: 1729631815 Timestamp [UCT]: 2024-10-22 21:16:55 Age [y:d:h:m:s]: 00:347:03:26:28
Block: 1137373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245576 RingCT/type: yes/0
Extra: 01c64e36cf66b7addd8e6bb34075c23a3b7b0606088314c2a27ca627ef575125cc0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50dd00f3568113eb76f68e19b8db4cff8e21a5a07a1cf82346d4c8f6a227809a 0.600000000000 1620852 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": 1137383, "vin": [ { "gen": { "height": 1137373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50dd00f3568113eb76f68e19b8db4cff8e21a5a07a1cf82346d4c8f6a227809a" } } ], "extra": [ 1, 198, 78, 54, 207, 102, 183, 173, 221, 142, 107, 179, 64, 117, 194, 58, 59, 123, 6, 6, 8, 131, 20, 194, 162, 124, 166, 39, 239, 87, 81, 37, 204, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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