Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34894ee4137fae500892c278445d68cda82c7bf2b03ca23cc7c5fc7634e3a7b1

Tx prefix hash: ad444113515323234f2cbfc182e622f22f8c9bce56946d2c898dbcd0d03ff470
Tx public key: ef7e9bf93d7fbe40383624cca0e810b1dcf86c8112f2506e207cc846901e59fc
Timestamp: 1736120220 Timestamp [UCT]: 2025-01-05 23:37:00 Age [y:d:h:m:s]: 00:162:14:44:47
Block: 1191070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115938 RingCT/type: yes/0
Extra: 01ef7e9bf93d7fbe40383624cca0e810b1dcf86c8112f2506e207cc846901e59fc0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af38705c4a6d06f432b09e0cbb728bbecf3c1e0a5059cf9c0a8e86f858fff261 0.600000000000 1677593 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": 1191080, "vin": [ { "gen": { "height": 1191070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af38705c4a6d06f432b09e0cbb728bbecf3c1e0a5059cf9c0a8e86f858fff261" } } ], "extra": [ 1, 239, 126, 155, 249, 61, 127, 190, 64, 56, 54, 36, 204, 160, 232, 16, 177, 220, 248, 108, 129, 18, 242, 80, 110, 32, 124, 200, 70, 144, 30, 89, 252, 2, 17, 0, 0, 0, 7, 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