Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f718398823073b7b7c631bcebf27cf8c9cdb254864318bdc1fa09206a138e942

Tx prefix hash: 213dc575e674a4bf0f3e0e3a636dacc5cc2d9d43e179289e95603f33ecaa8f3d
Tx public key: ed5eab52c6a1ed33e83e02c45ead398b6e3c166b1612eaf98254980fa9bc7a68
Timestamp: 1763430850 Timestamp [UCT]: 2025-11-18 01:54:10 Age [y:d:h:m:s]: 00:010:04:34:32
Block: 1414495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7294 RingCT/type: yes/0
Extra: 01ed5eab52c6a1ed33e83e02c45ead398b6e3c166b1612eaf98254980fa9bc7a6802110000000243b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a05a8307d5efe8d00509c90ad71a2c79ddd61bab405fa1cb1b58ba657dc8a6e5 0.600000000000 1902984 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": 1414505, "vin": [ { "gen": { "height": 1414495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a05a8307d5efe8d00509c90ad71a2c79ddd61bab405fa1cb1b58ba657dc8a6e5" } } ], "extra": [ 1, 237, 94, 171, 82, 198, 161, 237, 51, 232, 62, 2, 196, 94, 173, 57, 139, 110, 60, 22, 107, 22, 18, 234, 249, 130, 84, 152, 15, 169, 188, 122, 104, 2, 17, 0, 0, 0, 2, 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