Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20a28a910c8d4e97eb230a52153074ac00f9e7fae16f2363c598255e690fca6a

Tx prefix hash: 0cf113b2753a5c0c82d81e5a427f048dc76e4b79d1d94816e3ad2d1d0f13fa1b
Tx public key: d57c41e7fa0c012cbd463657a87b382d58ca855834c951017299cd6713180253
Timestamp: 1712250798 Timestamp [UCT]: 2024-04-04 17:13:18 Age [y:d:h:m:s]: 01:005:02:58:43
Block: 993280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264643 RingCT/type: yes/0
Extra: 01d57c41e7fa0c012cbd463657a87b382d58ca855834c951017299cd67131802530211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be0c3f56c66e7aaf8dbeac623e6b1f55732a136b829bfb0c3f9afbc8ac89418f 0.600000000000 1453666 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": 993290, "vin": [ { "gen": { "height": 993280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be0c3f56c66e7aaf8dbeac623e6b1f55732a136b829bfb0c3f9afbc8ac89418f" } } ], "extra": [ 1, 213, 124, 65, 231, 250, 12, 1, 44, 189, 70, 54, 87, 168, 123, 56, 45, 88, 202, 133, 88, 52, 201, 81, 1, 114, 153, 205, 103, 19, 24, 2, 83, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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