Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdac24f9edeb3fc24e1d8677bd773bb9c218e4bfd5bb99aaa7d549fbbf5fb77b

Tx prefix hash: 089389facf2923fe35044a1d430125469fbb5ea056116b2d24c1ff917d4cc253
Tx public key: fb5f72a3368717b09ae83f5e8347ced88d73b00346026c552ddd03fb14f430a9
Timestamp: 1697430159 Timestamp [UCT]: 2023-10-16 04:22:39 Age [y:d:h:m:s]: 01:197:00:37:15
Block: 870645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401860 RingCT/type: yes/0
Extra: 01fb5f72a3368717b09ae83f5e8347ced88d73b00346026c552ddd03fb14f430a902110000000233af99f4000000000000000000

1 output(s) for total of 0.800187420000 dcy

stealth address amount amount idx
00: 645f1459c7e74f26a86ca32b159a5291bcbf0837b3f08a051e6541d3966d87e0 0.800187420000 1325528 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": 870655, "vin": [ { "gen": { "height": 870645 } } ], "vout": [ { "amount": 800187420, "target": { "key": "645f1459c7e74f26a86ca32b159a5291bcbf0837b3f08a051e6541d3966d87e0" } } ], "extra": [ 1, 251, 95, 114, 163, 54, 135, 23, 176, 154, 232, 63, 94, 131, 71, 206, 216, 141, 115, 176, 3, 70, 2, 108, 85, 45, 221, 3, 251, 20, 244, 48, 169, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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