Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 170b5f5cc8362ded05ab4252b522cfea04824d441c6f3e459b40c1e5b31f0836

Tx prefix hash: cc2af33b9cecb6fa4bd454371ba1441dc4f7a61666f667beab7dffbd0dec3446
Tx public key: f31ec021f0ba14b817df9419d9538ea3c527466837d1c9f36962d520a87b6c9a
Timestamp: 1711668277 Timestamp [UCT]: 2024-03-28 23:24:37 Age [y:d:h:m:s]: 00:336:09:24:01
Block: 988495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240467 RingCT/type: yes/0
Extra: 01f31ec021f0ba14b817df9419d9538ea3c527466837d1c9f36962d520a87b6c9a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2802c4cb5cc9ee4bebe4530375e520af906ac6bf8b208e65ea6e090a964558b3 0.600000000000 1448774 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": 988505, "vin": [ { "gen": { "height": 988495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2802c4cb5cc9ee4bebe4530375e520af906ac6bf8b208e65ea6e090a964558b3" } } ], "extra": [ 1, 243, 30, 192, 33, 240, 186, 20, 184, 23, 223, 148, 25, 217, 83, 142, 163, 197, 39, 70, 104, 55, 209, 201, 243, 105, 98, 213, 32, 168, 123, 108, 154, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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