Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d69d050ae36b101a91a914fa65d6e08f139941ff681f0bf60b3f328c0c8b01a

Tx prefix hash: 7fb0e2d7bd73e7fa021e565140698a7e933f4f8dce605e840955bd85ae72a877
Tx public key: 56c7b1a15fced1b8bbb5a119e4e514df9e60ac8ecb9ac90371796f2e76bd5065
Timestamp: 1743853344 Timestamp [UCT]: 2025-04-05 11:42:24 Age [y:d:h:m:s]: 00:262:12:34:57
Block: 1254818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185393 RingCT/type: yes/0
Extra: 0156c7b1a15fced1b8bbb5a119e4e514df9e60ac8ecb9ac90371796f2e76bd50650211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 573d90873f5b96aab3a1b5ee06affbdd5d855b3a84541f45ed1438984c087b8a 0.600000000000 1741899 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": 1254828, "vin": [ { "gen": { "height": 1254818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "573d90873f5b96aab3a1b5ee06affbdd5d855b3a84541f45ed1438984c087b8a" } } ], "extra": [ 1, 86, 199, 177, 161, 95, 206, 209, 184, 187, 181, 161, 25, 228, 229, 20, 223, 158, 96, 172, 142, 203, 154, 201, 3, 113, 121, 111, 46, 118, 189, 80, 101, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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