Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ff00bc80c964d1353be77eedacf29885d667a5c68cb3992d517f5b6e5d550bd

Tx prefix hash: 4588e491611b0498111fffb806aabe13a255f8c37216fa1cdd20df25459cb397
Tx public key: a0d4fb5533bc1a5a1dd330b9ce7e543f2b0628a625ef2f40ae91a892fdfd4312
Timestamp: 1765978556 Timestamp [UCT]: 2025-12-17 13:35:56 Age [y:d:h:m:s]: 00:019:10:52:04
Block: 1435599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13956 RingCT/type: yes/0
Extra: 01a0d4fb5533bc1a5a1dd330b9ce7e543f2b0628a625ef2f40ae91a892fdfd4312021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 979ce7ced184a8001da437e94f50979b4d900616278c2607b7aba5873a800deb 0.600000000000 1924396 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": 1435609, "vin": [ { "gen": { "height": 1435599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "979ce7ced184a8001da437e94f50979b4d900616278c2607b7aba5873a800deb" } } ], "extra": [ 1, 160, 212, 251, 85, 51, 188, 26, 90, 29, 211, 48, 185, 206, 126, 84, 63, 43, 6, 40, 166, 37, 239, 47, 64, 174, 145, 168, 146, 253, 253, 67, 18, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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