Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5e27ef1e6c49f47d0c634b3a5beb6dcd3f5743a1b718d645e29dc85216607f

Tx prefix hash: 49b974928263d2795921332d143cc1e6521fa058bbcf0e4eb76b08755bfbba2d
Tx public key: 9e35fbb356af40c9281d45da419c193d26cbe8d17c8332597b68669ddb0d1f26
Timestamp: 1734106163 Timestamp [UCT]: 2024-12-13 16:09:23 Age [y:d:h:m:s]: 00:101:17:10:03
Block: 1174420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72455 RingCT/type: yes/0
Extra: 019e35fbb356af40c9281d45da419c193d26cbe8d17c8332597b68669ddb0d1f260211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b448c0db0c27b043fcf228c4f9613b33e54fd0a2153fc4d620a04c95474c78c4 0.600000000000 1660569 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": 1174430, "vin": [ { "gen": { "height": 1174420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b448c0db0c27b043fcf228c4f9613b33e54fd0a2153fc4d620a04c95474c78c4" } } ], "extra": [ 1, 158, 53, 251, 179, 86, 175, 64, 201, 40, 29, 69, 218, 65, 156, 25, 61, 38, 203, 232, 209, 124, 131, 50, 89, 123, 104, 102, 157, 219, 13, 31, 38, 2, 17, 0, 0, 0, 4, 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