Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4067dfe6fea61dcf7ff12419367d926f9c9ef7cbb691f630aed58f3d113f819

Tx prefix hash: c50a0989386d930312eb248c76f62ac95209c9c1d62a5b2e64a1b892c55e2976
Tx public key: 7405c4deb936253f306009ffce12ea1bac0e676a86e5b408023aace6e6895014
Timestamp: 1696388918 Timestamp [UCT]: 2023-10-04 03:08:38 Age [y:d:h:m:s]: 01:237:23:49:55
Block: 862007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431187 RingCT/type: yes/0
Extra: 017405c4deb936253f306009ffce12ea1bac0e676a86e5b408023aace6e6895014021100000001faf35c9c000000000000000000

1 output(s) for total of 0.854698638000 dcy

stealth address amount amount idx
00: 9e25570b8244939df03c7e4fdf24413e6e7cfd782eca81e11f9d58a4b8c06959 0.854698638000 1316387 of 0

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": 862017, "vin": [ { "gen": { "height": 862007 } } ], "vout": [ { "amount": 854698638, "target": { "key": "9e25570b8244939df03c7e4fdf24413e6e7cfd782eca81e11f9d58a4b8c06959" } } ], "extra": [ 1, 116, 5, 196, 222, 185, 54, 37, 63, 48, 96, 9, 255, 206, 18, 234, 27, 172, 14, 103, 106, 134, 229, 180, 8, 2, 58, 172, 230, 230, 137, 80, 20, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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