Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b080dcb00c36e40a086c3ceb4b258e84c259210fdb5812e98696cdaf80361d1

Tx prefix hash: 5db0accd45e082b8b781f2b6ad7b43998234f6b6fc13f3229011836a33685204
Tx public key: f80c59cd7b0d53962691f55016d4a6d1cceee3d42128b527c89eb2557d86ed75
Timestamp: 1673471308 Timestamp [UCT]: 2023-01-11 21:08:28 Age [y:d:h:m:s]: 02:122:14:58:09
Block: 672668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609342 RingCT/type: yes/0
Extra: 01f80c59cd7b0d53962691f55016d4a6d1cceee3d42128b527c89eb2557d86ed7502110000000552542ceb000000000000000000

1 output(s) for total of 3.623861838000 dcy

stealth address amount amount idx
00: 3c327c948daa90fdba77c1b7b7a5269a9c84e4cbc28879f761773d0451196680 3.623861838000 1114233 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": 672678, "vin": [ { "gen": { "height": 672668 } } ], "vout": [ { "amount": 3623861838, "target": { "key": "3c327c948daa90fdba77c1b7b7a5269a9c84e4cbc28879f761773d0451196680" } } ], "extra": [ 1, 248, 12, 89, 205, 123, 13, 83, 150, 38, 145, 245, 80, 22, 212, 166, 209, 204, 238, 227, 212, 33, 40, 181, 39, 200, 158, 178, 85, 125, 134, 237, 117, 2, 17, 0, 0, 0, 5, 82, 84, 44, 235, 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