Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa58d64e3ffd830f95c7c5c2114db74da58181982842654f8cbe9bc33f736ea3

Tx prefix hash: 44bf2064662e0a94717038c73cab5b4e9ebd5e10dbb889c227240a55d84a383f
Tx public key: 39eebc02c7d81277db5250d20a994423fd287cd0860a5f4ee50e4b2f2ae2fe08
Timestamp: 1720462199 Timestamp [UCT]: 2024-07-08 18:09:59 Age [y:d:h:m:s]: 00:281:19:06:52
Block: 1061394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201337 RingCT/type: yes/0
Extra: 0139eebc02c7d81277db5250d20a994423fd287cd0860a5f4ee50e4b2f2ae2fe08021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d49095647e774780d525b1d66f8b390b45a8b0827f61c2d785134291190fc84 0.600000000000 1531885 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": 1061404, "vin": [ { "gen": { "height": 1061394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d49095647e774780d525b1d66f8b390b45a8b0827f61c2d785134291190fc84" } } ], "extra": [ 1, 57, 238, 188, 2, 199, 216, 18, 119, 219, 82, 80, 210, 10, 153, 68, 35, 253, 40, 124, 208, 134, 10, 95, 78, 229, 14, 75, 47, 42, 226, 254, 8, 2, 17, 0, 0, 0, 1, 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