Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81f02f7917afacd973e05e050f391019eb3338d41668e56d69afe7b1ed1ecb1c

Tx prefix hash: 83cbe159f3a9844f6e6578e0b55f15f8ea995560e5ad9da18f3468b609c9f9b3
Tx public key: e5cfd4406df934b3fc29597a23d96a2db818e42606c4f155da43c5071245e7f8
Timestamp: 1724728962 Timestamp [UCT]: 2024-08-27 03:22:42 Age [y:d:h:m:s]: 00:253:17:06:33
Block: 1096750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181218 RingCT/type: yes/0
Extra: 01e5cfd4406df934b3fc29597a23d96a2db818e42606c4f155da43c5071245e7f8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 260ab6fe4254f0f11381a16789f8260ad8f0c698c0a6882acea8d2ea529a3c68 0.600000000000 1571945 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": 1096760, "vin": [ { "gen": { "height": 1096750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "260ab6fe4254f0f11381a16789f8260ad8f0c698c0a6882acea8d2ea529a3c68" } } ], "extra": [ 1, 229, 207, 212, 64, 109, 249, 52, 179, 252, 41, 89, 122, 35, 217, 106, 45, 184, 24, 228, 38, 6, 196, 241, 85, 218, 67, 197, 7, 18, 69, 231, 248, 2, 17, 0, 0, 0, 2, 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