Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f82ea3eabc17c7a55a4e141882a8b686066c7904c68c4e9e27c631e171bda32a

Tx prefix hash: 9a77f4c11559995d2573732b775ed37ca7552b19639143016b50646e11e930de
Tx public key: 849cfbcc4c92020e97cdb52d44acd3bbc691035a8fd3e4f5aea241b99d58de25
Timestamp: 1725098577 Timestamp [UCT]: 2024-08-31 10:02:57 Age [y:d:h:m:s]: 00:052:21:14:33
Block: 1099831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37841 RingCT/type: yes/0
Extra: 01849cfbcc4c92020e97cdb52d44acd3bbc691035a8fd3e4f5aea241b99d58de2502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851878468d13ade8e4f51cc4cae8bf4400868ea7ccf78467db5a1680ac6f6acd 0.600000000000 1575800 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": 1099841, "vin": [ { "gen": { "height": 1099831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851878468d13ade8e4f51cc4cae8bf4400868ea7ccf78467db5a1680ac6f6acd" } } ], "extra": [ 1, 132, 156, 251, 204, 76, 146, 2, 14, 151, 205, 181, 45, 68, 172, 211, 187, 198, 145, 3, 90, 143, 211, 228, 245, 174, 162, 65, 185, 157, 88, 222, 37, 2, 17, 0, 0, 0, 12, 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