Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1b380d6c0adf288bfbf39916e885b074cb9eb17bffc6ad5c0a5894277c0c825

Tx prefix hash: 2cb661b4d4b59b00b3c922498fc3b7abc8e3b8eb38507bf0ad66c985821162c8
Tx public key: 5f39cc704ae3c661acb8db4510f150031cfcf13e4f6bba4725290b2c3d86c303
Timestamp: 1755289340 Timestamp [UCT]: 2025-08-15 20:22:20 Age [y:d:h:m:s]: 00:054:08:28:06
Block: 1347423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38523 RingCT/type: yes/0
Extra: 015f39cc704ae3c661acb8db4510f150031cfcf13e4f6bba4725290b2c3d86c30302110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4d63b31ed270207989777683eeaa629cdb80aa0cb46b9e6700ad809c0ae0775 0.600000000000 1835340 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": 1347433, "vin": [ { "gen": { "height": 1347423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4d63b31ed270207989777683eeaa629cdb80aa0cb46b9e6700ad809c0ae0775" } } ], "extra": [ 1, 95, 57, 204, 112, 74, 227, 198, 97, 172, 184, 219, 69, 16, 241, 80, 3, 28, 252, 241, 62, 79, 107, 186, 71, 37, 41, 11, 44, 61, 134, 195, 3, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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