Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07dad3f6c44dfddd1997fc25737fc4e011c4ba325dc41b6e26d08c65adbe67b1

Tx prefix hash: 083414c802ad9da8991b98cd44c7cd749e532256770046e68a44c83464b34538
Tx public key: db5d7e8d4f6d19ee2e66454f8deb94a25703f77ee5c6b97991b0a60f31ffa7d8
Timestamp: 1751682190 Timestamp [UCT]: 2025-07-05 02:23:10 Age [y:d:h:m:s]: 00:132:11:17:41
Block: 1318987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92992 RingCT/type: yes/0
Extra: 01db5d7e8d4f6d19ee2e66454f8deb94a25703f77ee5c6b97991b0a60f31ffa7d802110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c427c3570d3e1394fc807f7b00374b42b2dd039d02903cc0f1aeb59fa857e1d3 0.600000000000 1806676 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": 1318997, "vin": [ { "gen": { "height": 1318987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c427c3570d3e1394fc807f7b00374b42b2dd039d02903cc0f1aeb59fa857e1d3" } } ], "extra": [ 1, 219, 93, 126, 141, 79, 109, 25, 238, 46, 102, 69, 79, 141, 235, 148, 162, 87, 3, 247, 126, 229, 198, 185, 121, 145, 176, 166, 15, 49, 255, 167, 216, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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