Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5ca44b66ce565ff5e352d7b2675daa1bf60ef8c811507bfd858f2f217492447

Tx prefix hash: 84b9159bac617aaa3762487afbbb305cb3a9e228073a91cab45f18b7bbe5f947
Tx public key: 4503d65916c806a078a5e9093ea2847fbc6ea3b2c6d7c3c5f5f61d5a26a09376
Timestamp: 1581640249 Timestamp [UCT]: 2020-02-14 00:30:49 Age [y:d:h:m:s]: 05:263:13:31:14
Block: 64506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1338883 RingCT/type: yes/0
Extra: 014503d65916c806a078a5e9093ea2847fbc6ea3b2c6d7c3c5f5f61d5a26a0937602110000000103d36d11000000000000000000

1 output(s) for total of 375.202441740000 dcy

stealth address amount amount idx
00: 5a0f1d8fa045ba2dda7843c0e8d1b322ef406d217dfaaaccfa5916348adb528f 375.202441740000 118987 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": 64516, "vin": [ { "gen": { "height": 64506 } } ], "vout": [ { "amount": 375202441740, "target": { "key": "5a0f1d8fa045ba2dda7843c0e8d1b322ef406d217dfaaaccfa5916348adb528f" } } ], "extra": [ 1, 69, 3, 214, 89, 22, 200, 6, 160, 120, 165, 233, 9, 62, 162, 132, 127, 188, 110, 163, 178, 198, 215, 195, 197, 245, 246, 29, 90, 38, 160, 147, 118, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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