Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105565953e04875de7f78654fbd827a0d7f575c4dbab04a41252fcce179a6ace

Tx prefix hash: a2b87599ce695681f41480394b73a3a0f98e0c8ef78dbcc5d0087e74cf7542cc
Tx public key: 410430cb704b31ae2787419f7ae40b4c16df8e49ce85614dd2064a801a432130
Timestamp: 1709621555 Timestamp [UCT]: 2024-03-05 06:52:35 Age [y:d:h:m:s]: 01:085:09:36:52
Block: 971520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322082 RingCT/type: yes/0
Extra: 01410430cb704b31ae2787419f7ae40b4c16df8e49ce85614dd2064a801a4321300211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8af26d11392fff1b2716207e3979114b8780badff3bb5876871d6ea2b3f35b7 0.600000000000 1431417 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": 971530, "vin": [ { "gen": { "height": 971520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8af26d11392fff1b2716207e3979114b8780badff3bb5876871d6ea2b3f35b7" } } ], "extra": [ 1, 65, 4, 48, 203, 112, 75, 49, 174, 39, 135, 65, 159, 122, 228, 11, 76, 22, 223, 142, 73, 206, 133, 97, 77, 210, 6, 74, 128, 26, 67, 33, 48, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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