Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77469f8ad238a720cebc22040dd2caa095ff2e86983ffe39003e554f61d3d6c1

Tx prefix hash: 9da0f0eda25344d6bbce596cde7c5e7774d9bf034dbb5e3a3694875682451727
Tx public key: 8803c9e2ad986ad1fca61317b86ed1db9fa9a47167e5664d11fc7c0e0313d4ab
Timestamp: 1577918702 Timestamp [UCT]: 2020-01-01 22:45:02 Age [y:d:h:m:s]: 05:151:14:33:27
Block: 36674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1258269 RingCT/type: yes/0
Extra: 018803c9e2ad986ad1fca61317b86ed1db9fa9a47167e5664d11fc7c0e0313d4ab021100000007d81c26c0000000000000000000

1 output(s) for total of 463.964408545000 dcy

stealth address amount amount idx
00: 4003ab2985f487e41e3816f9a5f64eb61eb4c4ebe86b8aab8181698f5e235b25 463.964408545000 62180 of 0

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": 36684, "vin": [ { "gen": { "height": 36674 } } ], "vout": [ { "amount": 463964408545, "target": { "key": "4003ab2985f487e41e3816f9a5f64eb61eb4c4ebe86b8aab8181698f5e235b25" } } ], "extra": [ 1, 136, 3, 201, 226, 173, 152, 106, 209, 252, 166, 19, 23, 184, 110, 209, 219, 159, 169, 164, 113, 103, 229, 102, 77, 17, 252, 124, 14, 3, 19, 212, 171, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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