Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff369303b86b9c9c46f5100233669e6903ed7a24fce9662043519c86422e10bf

Tx prefix hash: b1ac46d111a341be4b93e1bad768a53fd0c67df33e6d22ca1ea961534b55ed92
Tx public key: 6458ed88a08d0f0cd1b06928f9f7a1b9c6c51c713cc89f6e28832b27c325d030
Timestamp: 1708315706 Timestamp [UCT]: 2024-02-19 04:08:26 Age [y:d:h:m:s]: 01:275:21:25:27
Block: 960686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455930 RingCT/type: yes/0
Extra: 016458ed88a08d0f0cd1b06928f9f7a1b9c6c51c713cc89f6e28832b27c325d0300211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18ed8b73a89064a4ced71867352dadb507311a43d4d027f190e2bf3105889362 0.600000000000 1420273 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": 960696, "vin": [ { "gen": { "height": 960686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18ed8b73a89064a4ced71867352dadb507311a43d4d027f190e2bf3105889362" } } ], "extra": [ 1, 100, 88, 237, 136, 160, 141, 15, 12, 209, 176, 105, 40, 249, 247, 161, 185, 198, 197, 28, 113, 60, 200, 159, 110, 40, 131, 43, 39, 195, 37, 208, 48, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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