Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f43bc567567b06c7360fcf4688c2c521caa1bf6b98c37a13b38cd10912f4363

Tx prefix hash: 05c7ba19e832f72f9e44b5f742b91841b004009ea0913c10e20ae384d023d632
Tx public key: c6b235324d75931d57d268b8a48e9e8940cf065db08e8161af542a8a8fb77210
Timestamp: 1717044778 Timestamp [UCT]: 2024-05-30 04:52:58 Age [y:d:h:m:s]: 00:309:15:40:26
Block: 1033056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221300 RingCT/type: yes/0
Extra: 01c6b235324d75931d57d268b8a48e9e8940cf065db08e8161af542a8a8fb772100211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 646db92c300bea3d0d4c2a0ef474d88c8be9be31870cdc6fa1f5a400fe69681d 0.600000000000 1501513 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": 1033066, "vin": [ { "gen": { "height": 1033056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "646db92c300bea3d0d4c2a0ef474d88c8be9be31870cdc6fa1f5a400fe69681d" } } ], "extra": [ 1, 198, 178, 53, 50, 77, 117, 147, 29, 87, 210, 104, 184, 164, 142, 158, 137, 64, 207, 6, 93, 176, 142, 129, 97, 175, 84, 42, 138, 143, 183, 114, 16, 2, 17, 0, 0, 0, 1, 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