Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13cc3190622b8818b6123952d0ceb153920ee677b847ab6f30b7bd83a0e24d63

Tx prefix hash: 97a876258941db9cbfc4a7cba46b8d41b38966658982b160856e0cd9cdc03308
Tx public key: 0ff85281b2d28e5e620c26c7707dc3a13cb79cf32917bcf95e5b2ee342eb784e
Timestamp: 1706761421 Timestamp [UCT]: 2024-02-01 04:23:41 Age [y:d:h:m:s]: 01:279:14:54:14
Block: 947778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458631 RingCT/type: yes/0
Extra: 010ff85281b2d28e5e620c26c7707dc3a13cb79cf32917bcf95e5b2ee342eb784e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65998befe76cbf14157676f6b677d24128163c77c4a8cc60412fd9aab5a2aae5 0.600000000000 1406136 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": 947788, "vin": [ { "gen": { "height": 947778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65998befe76cbf14157676f6b677d24128163c77c4a8cc60412fd9aab5a2aae5" } } ], "extra": [ 1, 15, 248, 82, 129, 178, 210, 142, 94, 98, 12, 38, 199, 112, 125, 195, 161, 60, 183, 156, 243, 41, 23, 188, 249, 94, 91, 46, 227, 66, 235, 120, 78, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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