Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38f882b309e6e03fb42ce052232526ba8a4379ef3d04081b3557215f2479243c

Tx prefix hash: 83a87e92de5ae5b9148fabb63aa050399050406c12417f0270ea609733926771
Tx public key: e51e943d6a8e1f743da3ee6614d7db14c1673d1be1be9b5a1181b2cb95ffdce4
Timestamp: 1732188579 Timestamp [UCT]: 2024-11-21 11:29:39 Age [y:d:h:m:s]: 01:030:07:24:15
Block: 1158507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280118 RingCT/type: yes/0
Extra: 01e51e943d6a8e1f743da3ee6614d7db14c1673d1be1be9b5a1181b2cb95ffdce4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba9ba5353a42692ef034d9000f60bc121bd8b046f52608e64fd898a663a99ed5 0.600000000000 1644136 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": 1158517, "vin": [ { "gen": { "height": 1158507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba9ba5353a42692ef034d9000f60bc121bd8b046f52608e64fd898a663a99ed5" } } ], "extra": [ 1, 229, 30, 148, 61, 106, 142, 31, 116, 61, 163, 238, 102, 20, 215, 219, 20, 193, 103, 61, 27, 225, 190, 155, 90, 17, 129, 178, 203, 149, 255, 220, 228, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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