Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e88cf1d96f1aae0178892fed8bcf52f44071c7d393778dd1ee19635f6decb76

Tx prefix hash: 0d0221efacbe4262748e7da5717c20983c2c08d0e2c724f7b5e989a3462b79cf
Tx public key: eb89cf02258d41da9a28f2a82f9a994f32535a35da3c38a2d1b923006cd2558f
Timestamp: 1707554002 Timestamp [UCT]: 2024-02-10 08:33:22 Age [y:d:h:m:s]: 01:084:12:52:02
Block: 954359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321487 RingCT/type: yes/0
Extra: 01eb89cf02258d41da9a28f2a82f9a994f32535a35da3c38a2d1b923006cd2558f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a57a1574a067385ab5100ebed2e48fbf3a140366a816bbc8e1144772dd6a7517 0.600000000000 1413639 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": 954369, "vin": [ { "gen": { "height": 954359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a57a1574a067385ab5100ebed2e48fbf3a140366a816bbc8e1144772dd6a7517" } } ], "extra": [ 1, 235, 137, 207, 2, 37, 141, 65, 218, 154, 40, 242, 168, 47, 154, 153, 79, 50, 83, 90, 53, 218, 60, 56, 162, 209, 185, 35, 0, 108, 210, 85, 143, 2, 17, 0, 0, 0, 4, 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