Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a3105e9c4b8ae689363749eee3389719532888c55401dc3559156416b9b3d2b

Tx prefix hash: acd545a280f6dd283b4f3c4ea46d9e4205f25819d2172bc25d72fe94fe78d352
Tx public key: 42254643b480eaea76c55b2419c41ab1b094e37b6cb3f36a53cc89ec86c525d3
Timestamp: 1721527706 Timestamp [UCT]: 2024-07-21 02:08:26 Age [y:d:h:m:s]: 00:173:13:46:54
Block: 1070219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124188 RingCT/type: yes/0
Extra: 0142254643b480eaea76c55b2419c41ab1b094e37b6cb3f36a53cc89ec86c525d302110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 862dee0d7c3b75d61a4883356c484ddddd398ba1f44009876794c8d527effd96 0.600000000000 1541960 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": 1070229, "vin": [ { "gen": { "height": 1070219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "862dee0d7c3b75d61a4883356c484ddddd398ba1f44009876794c8d527effd96" } } ], "extra": [ 1, 66, 37, 70, 67, 180, 128, 234, 234, 118, 197, 91, 36, 25, 196, 26, 177, 176, 148, 227, 123, 108, 179, 243, 106, 83, 204, 137, 236, 134, 197, 37, 211, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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