Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7494961495ff73b8c71a3275243daa82bef16a954b9b7065a79b4d1e80a8e5a

Tx prefix hash: b3a7f5474b3377ab5cb90ade543d85998f8e56e7b6a7aa30a34213a5e079ee73
Tx public key: a3f48f64b5462852206a194466ee5c1add48e7754e24953349735d06d76b0540
Timestamp: 1704187201 Timestamp [UCT]: 2024-01-02 09:20:01 Age [y:d:h:m:s]: 01:302:23:37:46
Block: 926452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475375 RingCT/type: yes/0
Extra: 01a3f48f64b5462852206a194466ee5c1add48e7754e24953349735d06d76b05400211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e7c84d1aa67ec975e391e15c02bab6d4279d26ea07b64ec9fabe1dfea59fe79 0.600000000000 1384236 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": 926462, "vin": [ { "gen": { "height": 926452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e7c84d1aa67ec975e391e15c02bab6d4279d26ea07b64ec9fabe1dfea59fe79" } } ], "extra": [ 1, 163, 244, 143, 100, 181, 70, 40, 82, 32, 106, 25, 68, 102, 238, 92, 26, 221, 72, 231, 117, 78, 36, 149, 51, 73, 115, 93, 6, 215, 107, 5, 64, 2, 17, 0, 0, 0, 4, 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