Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aece15037a2138edc9ec8aaafb45cec6f84cf8316660f48dff9504a24c9caf8e

Tx prefix hash: ec4b01a8a83275ef24125742ffa7c057c805a198b5ba78c8cc038069e6a93e24
Tx public key: bb6d7df0a4d6e3885cb2eddaa85cbe2796903fb85de0b1c764fa7fa4673db427
Timestamp: 1745200508 Timestamp [UCT]: 2025-04-21 01:55:08 Age [y:d:h:m:s]: 00:023:20:52:56
Block: 1265958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17093 RingCT/type: yes/0
Extra: 01bb6d7df0a4d6e3885cb2eddaa85cbe2796903fb85de0b1c764fa7fa4673db4270211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d46c9c3e63677da2e0a228b02a6a098036f7aa6d33bbe82688a4cfe46fa4b979 0.600000000000 1753171 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": 1265968, "vin": [ { "gen": { "height": 1265958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d46c9c3e63677da2e0a228b02a6a098036f7aa6d33bbe82688a4cfe46fa4b979" } } ], "extra": [ 1, 187, 109, 125, 240, 164, 214, 227, 136, 92, 178, 237, 218, 168, 92, 190, 39, 150, 144, 63, 184, 93, 224, 177, 199, 100, 250, 127, 164, 103, 61, 180, 39, 2, 17, 0, 0, 0, 5, 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