Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b88b8117f752523d59ec255bee925ec0f4c8e746cd725693c2fae7129310fcf

Tx prefix hash: f19a2b250f13cb7505b652bef5edd9507a7b85c31f4085ec1be2407e38317640
Tx public key: 2c69b36b6cf27f067fcdf5ee280d66a71cd8cb1bc0589d394755e29e7c49f549
Timestamp: 1683713498 Timestamp [UCT]: 2023-05-10 10:11:38 Age [y:d:h:m:s]: 01:190:17:21:06
Block: 756977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397727 RingCT/type: yes/0
Extra: 012c69b36b6cf27f067fcdf5ee280d66a71cd8cb1bc0589d394755e29e7c49f549021100000003b3164c24000000000000000000

1 output(s) for total of 1.904676203000 dcy

stealth address amount amount idx
00: e88501c0a80c670d099d6eb516c851d12c8c70a603d72032f8f08229c5f709a3 1.904676203000 1205382 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": 756987, "vin": [ { "gen": { "height": 756977 } } ], "vout": [ { "amount": 1904676203, "target": { "key": "e88501c0a80c670d099d6eb516c851d12c8c70a603d72032f8f08229c5f709a3" } } ], "extra": [ 1, 44, 105, 179, 107, 108, 242, 127, 6, 127, 205, 245, 238, 40, 13, 102, 167, 28, 216, 203, 27, 192, 88, 157, 57, 71, 85, 226, 158, 124, 73, 245, 73, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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