Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 380f0194ff662b9c31aa01700c72b4edd39075535be3fb299570493c499657bc

Tx prefix hash: a998811b8aa2f5400709315c426c4416a21bf0c39680bae35bf5e526dc889d4e
Tx public key: cd1da2f912e987a2e636970f68a40b7a680ccbd9e752435238db571fb33f12fd
Timestamp: 1730457162 Timestamp [UCT]: 2024-11-01 10:32:42 Age [y:d:h:m:s]: 00:161:05:40:58
Block: 1144161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115087 RingCT/type: yes/0
Extra: 01cd1da2f912e987a2e636970f68a40b7a680ccbd9e752435238db571fb33f12fd0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5fc720018b7032d3f55d2ff2d6dcc805d3b8ac8fd031bc3fd4f406cba763bb2 0.600000000000 1628284 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": 1144171, "vin": [ { "gen": { "height": 1144161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5fc720018b7032d3f55d2ff2d6dcc805d3b8ac8fd031bc3fd4f406cba763bb2" } } ], "extra": [ 1, 205, 29, 162, 249, 18, 233, 135, 162, 230, 54, 151, 15, 104, 164, 11, 122, 104, 12, 203, 217, 231, 82, 67, 82, 56, 219, 87, 31, 179, 63, 18, 253, 2, 17, 0, 0, 0, 2, 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