Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c07c20b5db260d34f746f0de98af2e1f827760565fdf675de8475a3e5a1001f6

Tx prefix hash: 7aeca3fedb06524b45284b64b45feef1b1f56dd68e3bf36c2af1f6b78d7bad18
Tx public key: 366cdb3182039950e11e28b5ebc345a89b7dd2df2943800515c8e3b369d7230a
Timestamp: 1729789710 Timestamp [UCT]: 2024-10-24 17:08:30 Age [y:d:h:m:s]: 00:240:00:10:19
Block: 1138678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171213 RingCT/type: yes/0
Extra: 01366cdb3182039950e11e28b5ebc345a89b7dd2df2943800515c8e3b369d7230a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41c8fed5ff171afb1b20b02617ef2f6940e2292fb44c050aaea93c87813eea02 0.600000000000 1622377 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": 1138688, "vin": [ { "gen": { "height": 1138678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c8fed5ff171afb1b20b02617ef2f6940e2292fb44c050aaea93c87813eea02" } } ], "extra": [ 1, 54, 108, 219, 49, 130, 3, 153, 80, 225, 30, 40, 181, 235, 195, 69, 168, 155, 125, 210, 223, 41, 67, 128, 5, 21, 200, 227, 179, 105, 215, 35, 10, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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