Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f4086aee0e10c5e0dfec3ebc4f0520dd4c16c20876da06a8031ed59492b09f8

Tx prefix hash: a20d620174e107db96aedcacc8071a5b9319222244976df502eeec9b964aa780
Tx public key: cf2a7c21ae5e3b9c1d0405e7eda140295a32e2aa8ce76e1760d9cf6c431b0ba2
Timestamp: 1684144764 Timestamp [UCT]: 2023-05-15 09:59:24 Age [y:d:h:m:s]: 01:201:23:54:39
Block: 760547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405798 RingCT/type: yes/0
Extra: 01cf2a7c21ae5e3b9c1d0405e7eda140295a32e2aa8ce76e1760d9cf6c431b0ba2021100000005faf35c9c000000000000000000

1 output(s) for total of 1.853498584000 dcy

stealth address amount amount idx
00: 979f37f68829ed33af8ac661ffcd50d961b2feebd37c133dc9c32b269a81e0d1 1.853498584000 1209160 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": 760557, "vin": [ { "gen": { "height": 760547 } } ], "vout": [ { "amount": 1853498584, "target": { "key": "979f37f68829ed33af8ac661ffcd50d961b2feebd37c133dc9c32b269a81e0d1" } } ], "extra": [ 1, 207, 42, 124, 33, 174, 94, 59, 156, 29, 4, 5, 231, 237, 161, 64, 41, 90, 50, 226, 170, 140, 231, 110, 23, 96, 217, 207, 108, 67, 27, 11, 162, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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