Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69887059c309b360d621b5b941ee213c76cfac87e8cce23ca8c1587848a71d16

Tx prefix hash: 2ab243ef7c67983c8ff1fa654a66b0ec9146e611dbb60572e38a56789a7a9ef6
Tx public key: 3444c1856c5f298718609918b9a8cd6810970c6cc59f7e64533bafc3cb874145
Timestamp: 1714701640 Timestamp [UCT]: 2024-05-03 02:00:40 Age [y:d:h:m:s]: 00:298:14:56:15
Block: 1013640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213429 RingCT/type: yes/0
Extra: 013444c1856c5f298718609918b9a8cd6810970c6cc59f7e64533bafc3cb8741450211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c79e40f4dbddd1add1e82f7982509a701c6cd3d109c6d65645c7c8c89f77a8f4 0.600000000000 1476511 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": 1013650, "vin": [ { "gen": { "height": 1013640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c79e40f4dbddd1add1e82f7982509a701c6cd3d109c6d65645c7c8c89f77a8f4" } } ], "extra": [ 1, 52, 68, 193, 133, 108, 95, 41, 135, 24, 96, 153, 24, 185, 168, 205, 104, 16, 151, 12, 108, 197, 159, 126, 100, 83, 59, 175, 195, 203, 135, 65, 69, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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