Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d71424e9d2507a40c0b0e5b5a52c7949d3be75f18099971dcda4a600580be6

Tx prefix hash: 323707eb65b1dce078ed8c78e999d6e697c4fe8d144de3b68b9cced10b234fd7
Tx public key: 9b23fff65dc903e95d656c1fdd6873f9e0365cf1f777a8eba3c35c3aaae5401f
Timestamp: 1704112291 Timestamp [UCT]: 2024-01-01 12:31:31 Age [y:d:h:m:s]: 01:010:19:23:44
Block: 925829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269060 RingCT/type: yes/0
Extra: 019b23fff65dc903e95d656c1fdd6873f9e0365cf1f777a8eba3c35c3aaae5401f0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcba21307890810d7b2e9b160d4fc36a3da92219c7e9d3ee3960f7cc7fb6c5bb 0.600000000000 1383599 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": 925839, "vin": [ { "gen": { "height": 925829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcba21307890810d7b2e9b160d4fc36a3da92219c7e9d3ee3960f7cc7fb6c5bb" } } ], "extra": [ 1, 155, 35, 255, 246, 93, 201, 3, 233, 93, 101, 108, 31, 221, 104, 115, 249, 224, 54, 92, 241, 247, 119, 168, 235, 163, 195, 92, 58, 170, 229, 64, 31, 2, 17, 0, 0, 0, 7, 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