Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 956fe60c73fe1004e3fe81364680717c85d90a93b7c9cf07ebda16c5ce04613a

Tx prefix hash: c3741f2556d1f6f24f60dbe3ae1541918aa80241d5d040a855ee72a5c57c70fd
Tx public key: 9b63dbabc515b1b9e071c9b169ff0c941c1094f10eb366cdc7271b2c30d350f4
Timestamp: 1705075244 Timestamp [UCT]: 2024-01-12 16:00:44 Age [y:d:h:m:s]: 01:080:04:36:58
Block: 933806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318404 RingCT/type: yes/0
Extra: 019b63dbabc515b1b9e071c9b169ff0c941c1094f10eb366cdc7271b2c30d350f40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdaa38cb4b08e07dce30ba23af211b4eb038281a8bb8750bf8e10e406eb9bf60 0.600000000000 1391788 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": 933816, "vin": [ { "gen": { "height": 933806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdaa38cb4b08e07dce30ba23af211b4eb038281a8bb8750bf8e10e406eb9bf60" } } ], "extra": [ 1, 155, 99, 219, 171, 197, 21, 177, 185, 224, 113, 201, 177, 105, 255, 12, 148, 28, 16, 148, 241, 14, 179, 102, 205, 199, 39, 27, 44, 48, 211, 80, 244, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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