Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39022ccab01f63c263acba8910b872cb8bbc20e7861770480098b314e3fd4f07

Tx prefix hash: a012f356edd50bed5f720956525a3eb5eeab7bd98a8c88672f9a9598b901d68e
Tx public key: 3c0475de66f8b77afe1a48e496fb7881436513e6ff696043349fb4f2f0471d4c
Timestamp: 1673879346 Timestamp [UCT]: 2023-01-16 14:29:06 Age [y:d:h:m:s]: 01:303:23:18:34
Block: 676050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478231 RingCT/type: yes/0
Extra: 013c0475de66f8b77afe1a48e496fb7881436513e6ff696043349fb4f2f0471d4c0211000000015ec35160000000000000000000

1 output(s) for total of 3.531552417000 dcy

stealth address amount amount idx
00: e1d06405ee1b274c66cb831aacff2218a445cff0bb32fe1eda9b939d29ddc61e 3.531552417000 1117751 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": 676060, "vin": [ { "gen": { "height": 676050 } } ], "vout": [ { "amount": 3531552417, "target": { "key": "e1d06405ee1b274c66cb831aacff2218a445cff0bb32fe1eda9b939d29ddc61e" } } ], "extra": [ 1, 60, 4, 117, 222, 102, 248, 183, 122, 254, 26, 72, 228, 150, 251, 120, 129, 67, 101, 19, 230, 255, 105, 96, 67, 52, 159, 180, 242, 240, 71, 29, 76, 2, 17, 0, 0, 0, 1, 94, 195, 81, 96, 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