Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a55481b934ed4c7bafd837dce399e6e70d8e8f8f6487b2870a431993925a3938

Tx prefix hash: 38c0d59c394bb957bdbc77f00f6dface6232769181bdfb008483022b4728deb4
Tx public key: f9ae0b8e735115a274fb60c173a6a09cfac56a3c0c3525e862bb1909e21d439c
Timestamp: 1703487601 Timestamp [UCT]: 2023-12-25 07:00:01 Age [y:d:h:m:s]: 01:031:06:00:16
Block: 920656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283645 RingCT/type: yes/0
Extra: 01f9ae0b8e735115a274fb60c173a6a09cfac56a3c0c3525e862bb1909e21d439c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46a8327ad93affc3a6c7a382702203af29fd1f59a59e960952b43853a9ae9a91 0.600000000000 1378336 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": 920666, "vin": [ { "gen": { "height": 920656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46a8327ad93affc3a6c7a382702203af29fd1f59a59e960952b43853a9ae9a91" } } ], "extra": [ 1, 249, 174, 11, 142, 115, 81, 21, 162, 116, 251, 96, 193, 115, 166, 160, 156, 250, 197, 106, 60, 12, 53, 37, 232, 98, 187, 25, 9, 226, 29, 67, 156, 2, 17, 0, 0, 0, 2, 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