Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a5f147c76ff5765619f4af237853092df5cf9f464175387c291fbf99becc053

Tx prefix hash: e5fef92889fae41501a661949b26da432a718043ed9df0ad7927271ea1e3b03e
Tx public key: 3b37645174d9f4038c647e10d028aab624f975fefdba7b1c2dae5b5f4e718555
Timestamp: 1728904804 Timestamp [UCT]: 2024-10-14 11:20:04 Age [y:d:h:m:s]: 00:041:07:57:21
Block: 1131384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29505 RingCT/type: yes/0
Extra: 013b37645174d9f4038c647e10d028aab624f975fefdba7b1c2dae5b5f4e718555021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ab1c26b5f179d230d51ea1e2f1a4ef3108f39911fe257d603e9762dbe20d56b 0.600000000000 1614283 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": 1131394, "vin": [ { "gen": { "height": 1131384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ab1c26b5f179d230d51ea1e2f1a4ef3108f39911fe257d603e9762dbe20d56b" } } ], "extra": [ 1, 59, 55, 100, 81, 116, 217, 244, 3, 140, 100, 126, 16, 208, 40, 170, 182, 36, 249, 117, 254, 253, 186, 123, 28, 45, 174, 91, 95, 78, 113, 133, 85, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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