Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97c19b75d47c2e6bd2e5e6a5355919bc49321a8f8a3e9457ecf58785c5e78061

Tx prefix hash: 9469f831347e2aa3ec6f3041b1179b9875ddf49da5176b5a7328f15076974bda
Tx public key: 61e806fdea9fefb7d1c336105df17bfd595897657f4b2921ec626019a4777c98
Timestamp: 1763503031 Timestamp [UCT]: 2025-11-18 21:57:11 Age [y:d:h:m:s]: 00:009:08:25:19
Block: 1415089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6697 RingCT/type: yes/0
Extra: 0161e806fdea9fefb7d1c336105df17bfd595897657f4b2921ec626019a4777c9802110000000343b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 917456f98739fa0f3465f98e52e2d470daa43f4e4cc35a6a80d05bb1d7ce4a8b 0.600000000000 1903584 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": 1415099, "vin": [ { "gen": { "height": 1415089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "917456f98739fa0f3465f98e52e2d470daa43f4e4cc35a6a80d05bb1d7ce4a8b" } } ], "extra": [ 1, 97, 232, 6, 253, 234, 159, 239, 183, 209, 195, 54, 16, 93, 241, 123, 253, 89, 88, 151, 101, 127, 75, 41, 33, 236, 98, 96, 25, 164, 119, 124, 152, 2, 17, 0, 0, 0, 3, 67, 181, 4, 113, 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