Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a3722f3d0b81f18458b3c084639f7380348c4827da07d453559cc6ed0e495df

Tx prefix hash: 803834cd257128ada83a29f2feb15bc91d7cd2777bffb1a9c21cb57961badaa3
Tx public key: 90cc3f1c894e9d9fc2d9660d38a7edc40ad160e80b79a9e42da7839ba407d29a
Timestamp: 1731556036 Timestamp [UCT]: 2024-11-14 03:47:16 Age [y:d:h:m:s]: 00:141:12:06:11
Block: 1153271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100960 RingCT/type: yes/0
Extra: 0190cc3f1c894e9d9fc2d9660d38a7edc40ad160e80b79a9e42da7839ba407d29a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7b57e81070628105321856bd8bbd7eb419e2b26bdb2f88b0268f65906c3cb56 0.600000000000 1638880 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": 1153281, "vin": [ { "gen": { "height": 1153271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7b57e81070628105321856bd8bbd7eb419e2b26bdb2f88b0268f65906c3cb56" } } ], "extra": [ 1, 144, 204, 63, 28, 137, 78, 157, 159, 194, 217, 102, 13, 56, 167, 237, 196, 10, 209, 96, 232, 11, 121, 169, 228, 45, 167, 131, 155, 164, 7, 210, 154, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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