Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8633048959ae89a253434f9d71cc2f4f36d6a0596b7cfd734f497911fe831c6

Tx prefix hash: 234790443bfe875219c0d5a6ace23a454f2c1a96949c301ae042aef1e6b783e2
Tx public key: 9fc9cfbb24f572d9f386051fcefe5e2d0a6dfb193b1438a287d5264b38fb1bb3
Timestamp: 1582990892 Timestamp [UCT]: 2020-02-29 15:41:32 Age [y:d:h:m:s]: 05:073:02:47:58
Block: 74226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1206545 RingCT/type: yes/0
Extra: 019fc9cfbb24f572d9f386051fcefe5e2d0a6dfb193b1438a287d5264b38fb1bb3021100000040724f989b000000000000000000

1 output(s) for total of 348.384839477000 dcy

stealth address amount amount idx
00: 1bfbe5dc1e70df25075cd8cc25cb0ec606060597d43525129bc5232ba0daecc8 348.384839477000 137245 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": 74236, "vin": [ { "gen": { "height": 74226 } } ], "vout": [ { "amount": 348384839477, "target": { "key": "1bfbe5dc1e70df25075cd8cc25cb0ec606060597d43525129bc5232ba0daecc8" } } ], "extra": [ 1, 159, 201, 207, 187, 36, 245, 114, 217, 243, 134, 5, 31, 206, 254, 94, 45, 10, 109, 251, 25, 59, 20, 56, 162, 135, 213, 38, 75, 56, 251, 27, 179, 2, 17, 0, 0, 0, 64, 114, 79, 152, 155, 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