Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0693d911c545d6fbd1ac489179eb9fd4e950aa5ff91786922a7d5cab879a902

Tx prefix hash: 6f9e3ed0d9e050cf0adbc072057fba51ab94b365ebea29fdadae7a23c9db0819
Tx public key: a475cb6dd3d4623290220c7e8d902f8d1da88a65299d741815d011c39c5e0785
Timestamp: 1707003206 Timestamp [UCT]: 2024-02-03 23:33:26 Age [y:d:h:m:s]: 01:062:17:11:57
Block: 949792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305880 RingCT/type: yes/0
Extra: 01a475cb6dd3d4623290220c7e8d902f8d1da88a65299d741815d011c39c5e078502110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2044a8ebb3cb072738828048c8aac677acfc22054f6e2d475bb53aa839dab2e0 0.600000000000 1408324 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": 949802, "vin": [ { "gen": { "height": 949792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2044a8ebb3cb072738828048c8aac677acfc22054f6e2d475bb53aa839dab2e0" } } ], "extra": [ 1, 164, 117, 203, 109, 211, 212, 98, 50, 144, 34, 12, 126, 141, 144, 47, 141, 29, 168, 138, 101, 41, 157, 116, 24, 21, 208, 17, 195, 156, 94, 7, 133, 2, 17, 0, 0, 0, 6, 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