Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d9a4ee8ed4bcf33c09073112d3b86842503c90c18b5d1c717d9d6783d9a9df1

Tx prefix hash: 4c1b3fdbbd4fe7b78adbaae5d987eb8b2f1b75a12d1ac5e79f8006d4bb1caff1
Tx public key: f10a1673934427e53c0749b6e711e8ee96bd0aa78d4d57cd26a6421274e490bc
Timestamp: 1656970522 Timestamp [UCT]: 2022-07-04 21:35:22 Age [y:d:h:m:s]: 02:226:03:27:12
Block: 536704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 682753 RingCT/type: yes/0
Extra: 01f10a1673934427e53c0749b6e711e8ee96bd0aa78d4d57cd26a6421274e490bc02110000000175e3f0e9000000000000000000

1 output(s) for total of 10.225322243000 dcy

stealth address amount amount idx
00: 9b1c563c734763f48639299f44574c4cb8db76664ec19d6fe7796d3278c5a0da 10.225322243000 966499 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": 536714, "vin": [ { "gen": { "height": 536704 } } ], "vout": [ { "amount": 10225322243, "target": { "key": "9b1c563c734763f48639299f44574c4cb8db76664ec19d6fe7796d3278c5a0da" } } ], "extra": [ 1, 241, 10, 22, 115, 147, 68, 39, 229, 60, 7, 73, 182, 231, 17, 232, 238, 150, 189, 10, 167, 141, 77, 87, 205, 38, 166, 66, 18, 116, 228, 144, 188, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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