Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ff9f548519d9ae7592c41d3fc90b04e2f8785728bf041a59ec573c8b3d88f6f

Tx prefix hash: b35dcffa1b760d6badcae3eaccbf1f07de2e27253fbd943297ce4625cd9e5284
Tx public key: fc6f4607fa1c43a09ca1212a8d6d69da05c2a7d5914694affd780695caf6c54b
Timestamp: 1751180685 Timestamp [UCT]: 2025-06-29 07:04:45 Age [y:d:h:m:s]: 00:215:19:32:58
Block: 1315050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152270 RingCT/type: yes/0
Extra: 01fc6f4607fa1c43a09ca1212a8d6d69da05c2a7d5914694affd780695caf6c54b021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33601038731981463e96c0547f576628656b19a6b6963b77d1d5b15b2d3f7a68 0.600000000000 1802703 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": 1315060, "vin": [ { "gen": { "height": 1315050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33601038731981463e96c0547f576628656b19a6b6963b77d1d5b15b2d3f7a68" } } ], "extra": [ 1, 252, 111, 70, 7, 250, 28, 67, 160, 156, 161, 33, 42, 141, 109, 105, 218, 5, 194, 167, 213, 145, 70, 148, 175, 253, 120, 6, 149, 202, 246, 197, 75, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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