Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6914504d79aeed91e9a79384179e7c37e2532ea1d5f83602523dc6311ea7de84

Tx prefix hash: b8b3f251f7e31fb98f8e4232606b48be1a8e5854731dba472146bfdf1fd710d5
Tx public key: aaf722f1e8222019aa9f908b8655e21ac1a64a8724fcad495a4575ae27dfc8e2
Timestamp: 1745873037 Timestamp [UCT]: 2025-04-28 20:43:57 Age [y:d:h:m:s]: 00:197:23:27:24
Block: 1271546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139197 RingCT/type: yes/0
Extra: 01aaf722f1e8222019aa9f908b8655e21ac1a64a8724fcad495a4575ae27dfc8e20211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0a7c4241e6cdeac7cdaa33be03f1323eae38e10e52af4d142ca32b625e59395 0.600000000000 1758809 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": 1271556, "vin": [ { "gen": { "height": 1271546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0a7c4241e6cdeac7cdaa33be03f1323eae38e10e52af4d142ca32b625e59395" } } ], "extra": [ 1, 170, 247, 34, 241, 232, 34, 32, 25, 170, 159, 144, 139, 134, 85, 226, 26, 193, 166, 74, 135, 36, 252, 173, 73, 90, 69, 117, 174, 39, 223, 200, 226, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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