Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6115d932b0358053c2559c717fbb81e1c86f1532ac22d7351f1aa6c2aba87431

Tx prefix hash: fb4d1c347947ede3e15434fd78b8464d2eb4350fc06515bf5824db9133f59c2c
Tx public key: ddc124ba3a23fe1804eaa01df3c989d91058ab372d9bc9588d72e5ea082b841f
Timestamp: 1676968533 Timestamp [UCT]: 2023-02-21 08:35:33 Age [y:d:h:m:s]: 02:004:15:15:34
Block: 701684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524870 RingCT/type: yes/0
Extra: 01ddc124ba3a23fe1804eaa01df3c989d91058ab372d9bc9588d72e5ea082b841f02110000000674b6d784000000000000000000

1 output(s) for total of 2.904220161000 dcy

stealth address amount amount idx
00: f6211dea31e3aa2c76207be88850314901e35582ddf0588febe3b4f9253caced 2.904220161000 1145171 of 0

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": 701694, "vin": [ { "gen": { "height": 701684 } } ], "vout": [ { "amount": 2904220161, "target": { "key": "f6211dea31e3aa2c76207be88850314901e35582ddf0588febe3b4f9253caced" } } ], "extra": [ 1, 221, 193, 36, 186, 58, 35, 254, 24, 4, 234, 160, 29, 243, 201, 137, 217, 16, 88, 171, 55, 45, 155, 201, 88, 141, 114, 229, 234, 8, 43, 132, 31, 2, 17, 0, 0, 0, 6, 116, 182, 215, 132, 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