Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43282765f425bb5e8650bb9b6cfee04bbb599668b751c5ae30350a83dc10b1ca

Tx prefix hash: abef95d3870857d2cf72e00c4740a231d98fa122854dd024d6964eb00a0d2614
Tx public key: 9d589480bb92ead8b7b6c985130999dd4597bd12a2fe599a6a591df9c75a52c0
Timestamp: 1706681635 Timestamp [UCT]: 2024-01-31 06:13:55 Age [y:d:h:m:s]: 01:057:03:35:06
Block: 947117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301917 RingCT/type: yes/0
Extra: 019d589480bb92ead8b7b6c985130999dd4597bd12a2fe599a6a591df9c75a52c002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcd8d318007884d7a62f7322aa4401f9f4ac3fe5ab289cb4118e9dfa5223e4b6 0.600000000000 1405465 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": 947127, "vin": [ { "gen": { "height": 947117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcd8d318007884d7a62f7322aa4401f9f4ac3fe5ab289cb4118e9dfa5223e4b6" } } ], "extra": [ 1, 157, 88, 148, 128, 187, 146, 234, 216, 183, 182, 201, 133, 19, 9, 153, 221, 69, 151, 189, 18, 162, 254, 89, 154, 106, 89, 29, 249, 199, 90, 82, 192, 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