Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61de5c5d8be13c2db76052219adb602f4f621ce71c8ddea65d33b10aa512cc02

Tx prefix hash: c5734555f3df9d635ede1d26be2ae09f81fa4619066c5184bee34858ce3cb7df
Tx public key: 14cf808df4eef92b4ee3a3b0bdd1e96134502c3d9ee64dbddfaef5c7a38d2b56
Timestamp: 1744316110 Timestamp [UCT]: 2025-04-10 20:15:10 Age [y:d:h:m:s]: 00:029:01:56:40
Block: 1258648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20796 RingCT/type: yes/0
Extra: 0114cf808df4eef92b4ee3a3b0bdd1e96134502c3d9ee64dbddfaef5c7a38d2b56021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be2ed14f23f1094b7d62476890b321743112c834cecc6ec508a4d3b224449c19 0.600000000000 1745785 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": 1258658, "vin": [ { "gen": { "height": 1258648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be2ed14f23f1094b7d62476890b321743112c834cecc6ec508a4d3b224449c19" } } ], "extra": [ 1, 20, 207, 128, 141, 244, 238, 249, 43, 78, 227, 163, 176, 189, 209, 233, 97, 52, 80, 44, 61, 158, 230, 77, 189, 223, 174, 245, 199, 163, 141, 43, 86, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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