Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a201917518151c1ce7bf492464fb81378f7ebea8b175dd60fb3db777f4576d

Tx prefix hash: a5c8cba311e877bb7d31e3b77313a0ff60e18d05ac1e7031ba851932651463cd
Tx public key: 71b8acc1feab1c98ee4b6b24d6d792d14fbc75fdf3ffab958266e694e9bf558a
Timestamp: 1730972840 Timestamp [UCT]: 2024-11-07 09:47:20 Age [y:d:h:m:s]: 00:138:02:54:13
Block: 1148438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98539 RingCT/type: yes/0
Extra: 0171b8acc1feab1c98ee4b6b24d6d792d14fbc75fdf3ffab958266e694e9bf558a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 102013f932cd9d9eb319a3ed7a5107d5fc371e58f2c7a8af04067520718b18e1 0.600000000000 1633281 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": 1148448, "vin": [ { "gen": { "height": 1148438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "102013f932cd9d9eb319a3ed7a5107d5fc371e58f2c7a8af04067520718b18e1" } } ], "extra": [ 1, 113, 184, 172, 193, 254, 171, 28, 152, 238, 75, 107, 36, 214, 215, 146, 209, 79, 188, 117, 253, 243, 255, 171, 149, 130, 102, 230, 148, 233, 191, 85, 138, 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