Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43784204d3d7707083383082e73f01d83dcaa01a87ec0b32a45f5ec82613d50e

Tx prefix hash: 565ef0d3c16aa3cd924d48a33c96b3dcc6d70154e70c1541cef89a911e84f582
Tx public key: 450c2b93c58af9262a9e2b5bc6fe2e923e751aae0e251136e252a2c9c3ae92ce
Timestamp: 1713491933 Timestamp [UCT]: 2024-04-19 01:58:53 Age [y:d:h:m:s]: 00:344:08:23:10
Block: 1003593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246176 RingCT/type: yes/0
Extra: 01450c2b93c58af9262a9e2b5bc6fe2e923e751aae0e251136e252a2c9c3ae92ce021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 790cdd78f2f47cacc94a851150203ed84d47db3dcf451c695db4de0405b4f204 0.600000000000 1464135 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": 1003603, "vin": [ { "gen": { "height": 1003593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "790cdd78f2f47cacc94a851150203ed84d47db3dcf451c695db4de0405b4f204" } } ], "extra": [ 1, 69, 12, 43, 147, 197, 138, 249, 38, 42, 158, 43, 91, 198, 254, 46, 146, 62, 117, 26, 174, 14, 37, 17, 54, 226, 82, 162, 201, 195, 174, 146, 206, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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