Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5a7a309551785e201fb6918fdd61c569e7b2aa012c4b9dfdbf27454ee90b197

Tx prefix hash: 016c6a579e1c63dff047f9fe5681b3aa69a6c8d63f8b7b811a7b26f3583d4088
Tx public key: be5f1557c0a6d1004e5fef501f4e4bd2fdb3f69a64d8e43f039df8fad1963176
Timestamp: 1724753163 Timestamp [UCT]: 2024-08-27 10:06:03 Age [y:d:h:m:s]: 01:068:22:03:04
Block: 1096956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307703 RingCT/type: yes/0
Extra: 01be5f1557c0a6d1004e5fef501f4e4bd2fdb3f69a64d8e43f039df8fad1963176021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94eaa6a1a859c44167ceac9fc91ffa9f605f9b3440c2a5f88ed36edc02fcf8a5 0.600000000000 1572195 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": 1096966, "vin": [ { "gen": { "height": 1096956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94eaa6a1a859c44167ceac9fc91ffa9f605f9b3440c2a5f88ed36edc02fcf8a5" } } ], "extra": [ 1, 190, 95, 21, 87, 192, 166, 209, 0, 78, 95, 239, 80, 31, 78, 75, 210, 253, 179, 246, 154, 100, 216, 228, 63, 3, 157, 248, 250, 209, 150, 49, 118, 2, 17, 0, 0, 0, 6, 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