Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62be449e38f5b1f27cabe3b76efe55e1d55b65093832385e43f61fc137e4055a

Tx prefix hash: 5c60ad5be95fd9b227d24c319b337783b5d9df1b32df47e29dd346cc974d6e81
Tx public key: c06fdfb2e0529ba59e71d6dd0ce92b4c5b462f0315c03935318b98e91bcae3a0
Timestamp: 1699811349 Timestamp [UCT]: 2023-11-12 17:49:09 Age [y:d:h:m:s]: 01:145:10:44:14
Block: 890185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365139 RingCT/type: yes/0
Extra: 01c06fdfb2e0529ba59e71d6dd0ce92b4c5b462f0315c03935318b98e91bcae3a002110000000375e3f0e9000000000000000000

1 output(s) for total of 0.689362348000 dcy

stealth address amount amount idx
00: ca308e9180df3907684e742b6127d1bc5ba0c2874c91c95309992fb7ed244898 0.689362348000 1346206 of 0

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": 890195, "vin": [ { "gen": { "height": 890185 } } ], "vout": [ { "amount": 689362348, "target": { "key": "ca308e9180df3907684e742b6127d1bc5ba0c2874c91c95309992fb7ed244898" } } ], "extra": [ 1, 192, 111, 223, 178, 224, 82, 155, 165, 158, 113, 214, 221, 12, 233, 43, 76, 91, 70, 47, 3, 21, 192, 57, 53, 49, 139, 152, 233, 27, 202, 227, 160, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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